Device-to-device communication mode

ABSTRACT

Systems and methods for a device-to-device communications mode are described. When two user equipment are within proximity of each other and other requirements are met, the user equipment are configured by their associated nodes to enter a device-to-device communication mode. In that mode, the user equipment receives messages from the other user equipment without the messages traversing the core network between their associated nodes.

BACKGROUND

A cellular network includes a number of nodes interconnected by a corenetwork. Each of the nodes defines a cell and can wirelessly communicatewith devices within the cell and associated with the node. For a messageto be communicated from a first device to a second device, the messagemay be transmitted from the first device to a first node associated withthe first device, from the first node through the core network to asecond node associated with the second device, and from the second nodeto the second device. A reply from the second device may traverse asimilar path in reverse, from the second device to the second node, fromthe second node through the core network to the first node, and from thefirst node to the first device.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be understood more fully from the detaileddescription given below and from the accompanying drawings of variousembodiments of the present invention, which, however, should not betaken to limit the present invention to the specific embodiments, butare for explanation and understanding only. Further, it should beunderstood that the drawings are not necessarily proportional or toscale.

FIG. 1 illustrates an embodiment of cellular network.

FIG. 2 is a communications timing diagram of a first user equipment(UE1) sending a message to a second user equipment (UE2) in a normalmode.

FIG. 3 is a communications timing diagram of a first user equipment(UE1) sending a message to a second user equipment (UE2) in adevice-to-device (d2d) mode.

FIG. 4 is a communications timing diagram of two user equipmentcommunicating in a cellular network.

FIG. 5 is a flowchart illustrating an embodiment of a method ofconfiguring a first device to communicate directly with a second device.

FIG. 6 is a flowchart illustrating an embodiment of a method of a firstdevice directly communicating with a second device.

FIG. 7 illustrates a functional block diagram of an exemplary electronicdevice, in accordance with one embodiment.

DETAILED DESCRIPTION

As noted above, a cellular network includes a number of nodesinterconnected by a core network. The core network is the central partof a telecommunication network that provides various services to userswho are connected via the nodes. One of the main functions is to routedata, such as user-to-user message data, from one node to another. Eachof the nodes defines a cell and can wirelessly communicate with deviceswithin the cell and associated with the node. A device associated with anode is in wireless data communication with a node, but not necessarilyin constant wireless data communication. For a message to becommunicated from a first device to a second device, the message may betransmitted from the first device to a first node associated with thefirst device, from the first node through the core network to a secondnode associated with the second device, and from the second node to thesecond device. A reply from the second device may traverse a similarpath in reverse, from the second device to the second node, from thesecond node through the core network to the first node, and from thefirst node to the first device.

Described herein is a method in which two devices communicate with eachother directly, bypassing the nodes and the core network, if certainrequirements are met. For example, two devices may be configured tocommunicate with each other directly if they are in close proximity toeach other. As a further example, two devices may be configured tocommunicate with each other directly if legal requirements are met.

Because the message path between the two devices is shorter,communication between the two devices may have improved quality due tofewer hops and reduced possibility of message drop. Further, the amountof traffic on the core network may be reduced. Such direct communicationmay be particularly useful for local information exchange within anintelligent home or enterprise private network. Direct communication mayalso be particularly useful between specific devices or devices inspecific frequency bands that do not have legal restrictions related tointerception of communication at the core network.

FIG. 1 illustrates an embodiment of cellular network 10. The cellularnetwork includes a first eNodeB (eNB1) 110 and a second eNodeB (eNB2)210 coupled to a core network 300. Although some embodiments describedherein refer generally to an LTE (Long Term Evolution) cellular network,it is to be appreciated that other aspects described herein may be usedin other networks. For example, aspects described herein may be used ina LAN (local area network) or a PAN (personal area network). Similarly,although terminology specific to LTE or other network standards may beused, it is to be appreciated that aspects may be applicable to othertypes of networks. For example, aspects described with respect to aneNodeB may be used with respect to a Node B, a base transceiver station(BTS), a base station, a server, a node or other wireless communicationhardware with which to communicate with user equipment (UEs) or mobilestations (MSs). The base station may include (1) a transceiver withwhich to receive wireless signals from user equipment and transmitwireless signals to user equipment and (2) a network interface tocommunicate with the core network. Thus, the base station couples theuser equipment to the cellular network 10.

The eNB1 110 has a communication range defining a first cell 115 and theeNB2 210 has a communication range defining a second cell 215. A firstuser equipment (UE1) 120 is located within the first cell 115 and ableto receive transmissions from the eNB1 110. The UE1 120 has acommunication range 125 encompassing the eNB1 110 and thus, the eNB1 110is able to receive transmissions from the UE1 120. Similarly, a seconduser equipment (UE2) 220 is located within the second cell 215 and ableto receive transmissions from the eNB2 210. The UE2 220 has acommunication range 225 encompassing the eNB2 210 and thus, the eNB2 210is able to receive transmissions from the UE2 220. The UE1 120 and UE2220 may include any device used directly by an end-user to communicate.For example, the UE1 120 and UE2 220 may be a hand-held telephone, atablet computer, a laptop computer equipped with a mobile broadbandadapter or any other device.

In a normal mode, for the UE1 120 to communicate a message to the UE2220, the UE1 120 transmits data to the eNB1 110, the eNB1 110 transmitsthe message through the core network 300 to the eNB2 210, and the eNB2210 transmits the message to the UE2 220. The core network 300 mayinclude a number of core network components 301-303 including a MobilityManagement Entity (MME), a Serving Gateway (SGW), a PDN [Packet DataNetwork] Gateway (PGW), a Home Subscriber Server (HSS), an IP MultimediaSystem (IMS), and other network elements. Thus, a message transmitted bythe UE1 120 may traverse the eNB1 110, the eNB2 210, and a number ofcore network components 301-303 before being received by the UE2 220.Additional details regarding the normal mode of communication aredescribed below with respect to FIG. 2.

However, as illustrated in FIG. 1, the UE1 120 and UE2 220 are eachwithin the communication range 125, 225 of the other and could eachreceive a message transmitted by the other. Thus, in a device-to-device(d2d) mode, the UE1 120 and the UE2 220 communicate directly with eachother, bypassing the eNB1 110, the core network 300, and the eNB2 210.This may improve the quality of communication between the UE1 120 andthe UE2 220 and reduces the amount of traffic on the core network 300.Additional details regarding the device-to-device (d2d) mode ofcommunication are described below with respect to FIG. 3.

It is to be appreciated that FIG. 1 illustrates a particularlyorientation of the UEs at a particularly point in time and that the UEsmay be mobile devices that, at other times, may be associated withdifferent eNodeBs, out of communication range of each other, out ofcommunication range of the network, turned off, or otherwise atdifferent locations. In particular, whereas FIG. 1 illustrates the firstUE1 120 and the second UE2 220 in proximity of each other, this is notnecessarily always the case.

FIG. 2 is a communications timing diagram of a first user equipment(UE1) 120 sending a message to a second user equipment (UE2) 220 in anormal mode. For the UE1 120 to send a message (or other data) to theUE2 220, the UE1 120 receives an uplink (UL) grant from the eNB1 110 ona downlink control channel. The downlink control channel (along withother channels) may be established during an association procedurebetween the user equipment and the eNodeB. The downlink control channelmay encode control data from the eNodeB to the user equipment. It is tobe appreciated that the terms “encode” and “decode” as used herein mayinclude or exclude encryption and decryption, compression anddecompression, modulation and demodulation, or other processing.

In one embodiment, the downlink control channel may be a PhysicalDownlink Control Channel (PDCCH). Thus, the grant may be received on thePDCCH of the eNB1 110 [PDCCH(1)]. Other information may also be receivedin the PDCCH(1), such as system information of the first node SI(1).Such system information may include a Master Information Block (MIB) andmultiple System Information Blocks (SIBs). The system information mayindicate a number of antennas of the node, system bandwidth, transmitpower, and information regarding channel configuration and scheduling.The system information may include a node identifier, such as a PLMN(Public Land Mobile Network) identifier or a LAI (Local Area Identity).The UL grant provides the UE1 120 with an indication of channelresources to be used by the UE1 120 to transmit the message (andpossibly additional messages) to the eNB1 110 on an uplink data channel.The channel resources may be one or more of a time period, a frequencyband, a spreading code, a frequency hop pattern, an electromagnetic (EM)polarity, or any other channel resource. A spreading code or a frequencyhop pattern may be one of a set of orthogonal waveforms used inspread-spectrum communication systems. Spread-spectrum communicationsystems also transmission of different data at the same time and at thesame frequency using different spreading codes (or frequency hopspatterns) and which can still be separated at the receiver.Electromagnetic polarity may be an orientation of the electromagneticwave. An electromagnetic wave with a single polarity may be referred toas “polarized light.” Two electromagnetic waves transmitted at the sametime and at the same frequency, but with different, perpendicularpolarities, may be separated at the receiver.

The uplink data channel may encode message data from the user equipmentto the eNodeB. In one embodiment, the uplink data channel may be aPhysical Uplink Shared Channel (PUSCH). Thus, the message may betransmitted on the PUSCH of the UE1 120 [PUSCH(1)] using the resourcesindicated by the UL grant.

Along with transmitting the message on the PUSCH(1), the UE1 120transmits control data to the eNB1 110 on an uplink control channel. Theuplink control channel may encode control data from the user equipmentto the eNodeB. In one embodiment, the uplink control channel may be aPhysical Uplink Control Channel (PUCCH). Thus, the control data may betransmitted on a PUCCH of the UE1 120 [PUCCH(1)]. The control data mayinclude, among other things, acknowledgement data such as ACK/NACK ofprior received signals and the eNB1 110 may use control data to makefuture decisions on (re)transmission, channel allocation, etc.

Because the UE2 220 is in proximity of the UE1 120, the UE2 220 may alsoreceive transmissions sent by the UE1 120. However, because the UE2 220does not have the UL grant information that the UE1 110 was given by theeNB1 110 (or the SI(1))), the UE2 220 does not expect to receive atransmission from UE1 120 or any other source. Thus, the UE2 220 thetreats the transmissions as noise and ignores them (as indicated bydashed arrows in FIG. 2).

Once the eNB1 110 decodes the message on the PUSCH(1), the eNB1 110transmits the message over the core network 300 to the eNB2 210.

The UE2 220 receives a downlink (DL) channel allocation (grant) from theeNB2 210 on a downlink control channel. In one embodiment, the downlinkcontrol channel may be a Physical Downlink Control Channel of the eNB2210 [PDCCH(2)]. The DL grant provides the UE2 220 with an indication ofa channel resource to be used by the UE2 220 to receive the message fromthe eNB2 210 on a downlink data channel. The downlink data channel mayencode message data from the eNodeB to the user equipment. In oneembodiment, the downlink data channel may be a Physical Downlink SharedChannel (PDSCH). Using the designated channel resource, the eNB2 210transmits the message to the UE2 220 and the UE2 220 receives it. Thus,the message may be received by the UE2 220 on the PDSCH of the eNB2 210[PDSCH(2)]). The UE2 220 may use control data received on the PDCCH(2)or from another source to decode the message. Thus, the UE2 220 receivesthe message originating from the UE1 120.

FIG. 3 is a communications timing diagram of a first user equipment(UE1) 120 sending a message to a second user equipment (UE2) 220 in adevice-to-device (d2d) mode. For the UE1 120 to send a message (or otherdata) to the UE2 220, the UE1 120 receives PDCCH(1) data from the eNB1110 on the PDCCH(1). The PDCCH(1) data may include, among other things,(a) system information of the first node SI(1) and (b) a channelallocation indicating a channel resource to be used by the UE1 120 totransmit the message on the PUSCH(1). The channel allocation may alsoindicate a channel resource to be used by the UE1 120 to transmitcontrol data on the PUCCH(1). The channel allocation in the PDCCH(1)data may be scrambled by an identifier of the UE1 120, such as the CRNTI(Cell Radio Network Temporary Identifier) of the UE1 120. The PDCCH(1)data may include additional information.

The PDCCH(1) data is also sent by the eNB1 110 over the core network 300to the eNB2 210 which transmits it to the UE2 220. The information maybe transmitted to the UE2 on the PDCCH(2) (or a modified version thereofthat includes this information), the PDSCH(2), a dedicated d2d channel,or any other channel. In one embodiment, at least a portion of thePDCCH(1) data is transmitted using Layer 3 (L3) signaling. For example,in one embodiment, the SI(1) of the PDCCH(1) data is transmitted usingL3 signaling on the PDSCH(2) while the channel allocation is transmittedon a modified PDCCH(2).

Because the PDCCH(1) data is received by the UE2 220, it is as thoughthe UE2 220 has decoded the PDCCH(1) from the eNB1 110 even though theUE2 220 is not within range of the eNB1 110. Thus, the transmission ofthe PDCCH(1) data by the eNB2 210 generates a proxy for the eNB1 110.

The UE1 120 transmits the message to the eNB1 110 on the PUSCH(1) usingthe channel resource specified in the channel allocation of the PDCCH(1)data. As described above with respect to the normal mode, along withtransmitting the message on the PUSCH(1), the UE1 120 may transmituplink control data to the eNB1 110 on the PUCCH(1) including, but notlimited to, ACK/NACK of prior signals. As above, because the UE2 220 isin proximity of the UE1 120, the UE2 220 may also receive transmissionssent by the UE1 120. Unlike above, however, the UE2 220 does have thechannel allocation that the UE1 110 was given by the eNB1 110 becausethe UE2 220 has received the PDCCH(1) data from the eNB2 210. Thus,rather than treating the transmissions as noise, the UE2 220 receivesand decodes the message transmitted on PUCCH(1) using the PDCCH(1) data(including, e.g., the SI(1) and the channel allocation).

Being in communication range of the UE1 120, the eNB1 110 also receivesthe message (and any uplink control data). However, in thedevice-to-device mode, the eNB1 110 does not transmit the message overthe core network to the eNB2 210 as in the normal mode. As discussedbelow, the eNB1 110 may use the uplink control data and message forother purposes (e.g., channel condition feedback and L3 measurementreports), but the eNB1 110 does not send the message over the corenetwork 300. Thus, the UE2 220 receives the message from the UE1 120without the message being transmitted over the core network 300.

FIG. 4 is a communications timing diagram of two user equipmentcommunicating in a cellular network. Whereas FIG. 2 illustrates a normalmode of communication and FIG. 3 illustrates a device-to-device (d2d)mode of communication, FIG. 4 illustrates switching from a normal modeof communication to a d2d mode of communication. Also, whereas FIG. 2and FIG. 3 illustrate a message from the UE1 110 to the UE2 210, FIG. 4illustrates messages in both directions.

The eNB1 110 transmits control data on the PDCCH(1) to the UE1 120 andthe UE1 120 transmits control data on the PUCCH(1) to the eNB1 110. TheUE2 220 may also receive this transmission, but in normal mode, treatsit as noise. The UE1 120 transmits a first message (msg1) intended forthe UE2 220 on the PUSCH(1) to the eNB1 110. The msg1 may be transmittedusing a channel resource indicated in an UL grant provided by the eNB1110 on the PDCCH(1). Although the UE2 220 may also receive thistransmission, it is treated as noise in the normal mode.

The eNB1 110 sends the msg1 over the core network 300 to the eNB2 210.The eNB2 210 transmits control data on the PDCCH(2) to the UE2 220 andtransmits the msg1 to the UE2 220 on the PDSCH(2). The msg1 may betransmitted using a channel resource indicated in a DL grant provided bythe eNB2 210 on the PDCCH(2).

To reply, the UE2 220 transmits the reply, a second message (msg2) tothe eNB2 210. The msg2 may be transmitted using a channel resourceindicated in an UL grant provided by the eNB2 210 on the PDCCH(2).Although the UE1 120 may also receive this transmission, it is treatedas noise in the normal mode.

The eNB2 210 sends the msg2 over the core network 300 to the eNB1 110.The eNB1 110 transmits msg2 to the UE1 120 on the PDSCH(1). The msg2 maybe transmitted using a channel resource indicated in a DL grant providedby the eNB1 110 on the PDCCH(1).

A decision may be made to switch the two user equipment 120, 220 fromthe normal mode into a device-to-device (d2d) mode. The decision may bebased on a detection that the UE1 120 and the UE2 220 are in proximityof each other. This detection may be based on the geographical locationof the user equipment or the APN (access point name) requested by theuser equipment or a combination of the two or any other method. Thedecision to switch the user equipment to the d2d mode may be performedby the core network 300, by the eNodeBs 110, 210, or any othercomponent. The decision may be based on a request transmitted by a user.

Once the decision to switch the devices to d2d mode has been made orcommunicated to the eNB1 110 and eNB2 210, they may co-ordinate witheach other to switch the UE1 120 and UE2 220 into d2d mode. Thiscoordination may include the exchange of messages directly between eachother (using, e.g., the X2-AP interface or a proprietary interface) orthey may exchange these messages using the CN (using, e.g., the S1-APinterface). As part of these messages they also exchange PDDCH data,including system information (SI(1) and SI(2)), channel allocationinformation, and other relevant information with each other. The eNodeBswill then send a message to switch their respective user equipment tod2d mode. The same or a different message may also include the durationfor which to remain in this mode until otherwise instructed. The same ora different message may also include the PDCCH data of the other eNodeB.This messaging may be done using L3 (RRC) signaling. The time ofswitching and the duration for which to remain in the d2d mode may besynchronized between the two UEs with the help of their eNodeBs. Theactual time/frequency or any other form of physical channel resourcesmay be configured using the PDCCH(1) and PDCCH(2) after the UEs areswitched to d2d mode and it shall last for the duration suggested in theRRC signaling message unless other conditions as indicated below aremet.

In the d2d mode, the UE1 120 transmits a third message (msg3) on thePUSCH(1) using the channel resource specified in the channel allocation.Because the UE2 220 is in proximity to the UE1 120, the UE2 220 mayreceive transmissions sent by the UE1 120. Because the UE2 220 hasreceived the PDCCH(1) data from the eNB2 210, the UE2 220 has thechannel allocation that the UE1 110 was given by the eNB1 110. Thus,rather than treating the transmission as noise, the UE2 220 receives anddecodes the msg3 transmitted on PUCCH(1) using the PDCCH(1) data(including, e.g., the SI(1) and the channel allocation). Thus, the UE2220 receives the msg3 from the UE1 120 without the message beingtransmitted over the core network 300. The UE2 210 may similar replywith a fourth message (msg4) that is not transmitted over the corenetwork 300.

When UE1 120 transmits the msg3, the msg3 is also received by the eNB1110. Similarly, when UE2 220 transmits the msg4, the msg4 is alsoreceived by the eNB2 210. The eNodeBs need not send the information overthe CN as in the normal mode of communication, but can still use thereceived transmission to decode L3 measurement reports.

The L3 measurement reports may be used by the eNodeBs to determinewhether to switch out of the d2d mode back into the normal mode. Forexample, the L3 measurement reports may indicate that one of the userequipment is moving out of coverage of the associated eNodeB and is tobe handed over to another eNodeB. If it is determined that the userequipment is to be switched back into normal mode, both user equipmentare provided instructions to switch to normal mode and decode the PDSCHof the associated node to receive messages.

The eNodeBs may also decode the ACK/NACK and channel condition feedbackof their associated user equipment transmitted on the PUCCH of theassociated user equipment. The eNodeBs may use this information tochange the uplink channel allocations given the user equipment fordevice-to-device communication. For example, if the number of NACKs ishigh or channel conditions unsatisfactory, the uplink channelallocations may be changed. The decision to change the uplink channelallocations may be made by both eNodeBs in conjunction using X2signaling, proprietary signaling, or other signaling between the twonodes (including or excluding the CN).

The UE1 120 or UE2 220 may implicitly release the channel allocationsmade to it via PDCCH(1) if it no longer has data to transmit in theuplink, even if the duration of uplink channel allocation configurationas configured by the eNodeB has not expired.

FIG. 5 is a flowchart illustrating an embodiment of a method 500 ofconfiguring a first device to communicate directly with a second device.The method 500 may be performed by processing logic that may includehardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (e.g., instructions executed by a processingdevice), firmware or a combination thereof. For example, the method 500may be performed by the first eNodeB 110 of FIG. 1. Also the flowchartis only suggestive and does not necessarily dictate the order in whichthe blocks or the functionality within each block have to be executed.The number of messages to be exchanged among the involved entities inorder to achieve the suggested functionality is not limited.

At block 510, the processing logic determines that a first deviceassociated with a first node of a network is to be configured tocommunicate directly with a second device associated with a second nodeof the network. The processing logic may make this determination inresponse to receiving a command from a core network. The processinglogic may make this determination in conjunction with other processinglogic (e.g., processing logic of the second node) using, e.g., L3signaling between two nodes. In one embodiment, the first device is afirst user equipment and the second device is a second user equipment.In one embodiment, the first node is a first base station and the secondnode is a second base station.

The determination may be based on determining that the first device andthe second device are in proximity of each other. It may be determinedthat the first device and second device are in proximity of each otherbased on and/or the APN (access point name) requested by the devices andthe geographical location of the devices. The first device and seconddevice may be in proximity of each other if the distance between them isless than a threshold, e.g., 100 km, 10 km, 1 km, etc. The determinationthat the first device is to be configured to communicate directly withthe second device may be based on a determination that suchconfiguration satisfies legal requirements, such as LI (LawfulInterception) requirements set forth by the FCC (Federal CommunicationsCommission). The determination may be based on determining a networkconfiguration of the devices. For example, it may be determined toconfigure the devices to communication directly based on a determinationthat the devices are part of a single-party sub-network (a contained anddefined sub-network owned by a single party), e.g., an intelligent homeor enterprise private network.

At block 520, the processing logic receives control parameters of acontrol channel from the second node. The control parameters may includedownlink control channel data of the second node. For example, theprocessing logic may receive control parameters typically communicatedon the PDCCH of the second node. The control parameters may includeSystem Information (SI) of the second node. The control parameters mayinclude a CRNTI (Cell Radio Network Temporary Identifier) of the seconddevice, a PUCCH/PUSCH Resource location allocated to the second device,and other information to decode transmissions of the second device. Thecontrol parameters may be received from the second node over an X2interface, a proprietary interface, or any other interface between thefirst and second node, including an interface through the core network.

At block 530, the processing logic transmits the control parametersreceived from the second node to the first device. Thus, the firstdevice receives the control parameters of the second node even thoughthe first device may not be within transmission range of the secondnode. In particular, the first device receives system information of thesecond node event though the first device may not be within transmissionrange of the second node and also receives information regarding channelallocations allocated by the second node even though the first devicemay not be within transmission range of the second node. The controlparameters may be transmitted to the first device using L3 signaling, L1signaling, other signaling, or some combination thereof.

At block 540, the processing logic determines channel resources toallocate. The channel resources may be one or more of a time period, afrequency band, a spreading code, a frequency hop pattern, anelectromagnetic (EM) polarity, or any other channel resource.

At block 550, the processing logic transmits information regarding theallocation of the channel resources to the first device. Informationregarding the allocated channel resources may be transmitted on thePDCCH from the first node to the first device. Information regarding theallocated channel resources may also be communicated to the seconddevice. This information regarding the allocated channel resources mayalso be communicated to second device. For example, the information maybe sent the second device by the second node on a modified PDCCH. Thesecond node may receive the information over an X2 interface, aproprietary interface or another interface which may or may not includethe CN.

Although described as separate transmissions in blocks 530 and 550, itis to be appreciated that the control parameters (including the systeminformation and user equipment identifying) and the informationregarding an allocated channel resource may be transmitted at the sametime or a different times and may be transmitted over the same channelor over different channels.

At block 560, the processing logic transmits instructions to the firstdevice to communicate directly with the second device using theallocated channel resources. The instructions may be transmitted usingL3 signaling, L1 signaling, or a combination thereof. The instructionsinclude instructions for the first device to determine message datatransmitted by the second device.

If the user equipment does not use all of the allocated channelresources the processing logic may receive a release of the grant or aportion thereof. For example, if there is no message data transmitted onthe PUSCH, the processing logic may receive a release of the grant fromthe user equipment. Such release may also be communicated to the othereNodeB and other user equipment.

FIG. 6 is a flowchart illustrating an embodiment of a method 600 ofcommunicating directly by a first device with a second device. Themethod 600 may be performed by processing logic that may includehardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (e.g., instructions executed by a processingdevice), firmware or a combination thereof. For example, the method 600may be performed by the first user equipment 120 of FIG. 1. Also theflowchart is only suggestive and does not necessarily dictate the orderin which the blocks or the functionality within each block have to beexecuted. The number of messages to be exchanged among the involvedentities in order to achieve the suggested functionality is not defined.

At block 610, the processing logic of a first device associated with afirst node receives instructions to communicate directly with a seconddevice associated with a second node.

At block 620, the processing logic receives control parameters of acontrol channel of the second node. For example, the processing logicmay receive information (from the first node or another source)information typically transmitted by the second node on the PDDCH of thesecond node. The control parameters may include system information andan indication of channel resources to be used in communicating directlywith the second device.

At block 630, the processing logic determines message data using thecontrol parameters. For example, the processing logic may receive atransmission from the second device on a PUSCH of the second device.Using the control parameters, the processing logic may decode the PUSCHof the second device and read the message data encoded thereon.

Thus, after receiving the instructions to communicate directly with thesecond device (at block 610), the first device can receive informationtypically on the PDCCH of the second node (at block 620), and the PUSCHof the second (at block 630). In contrast, when the device has notreceived instructions to communicate directly with the second device,the first device receives none of this information. Rather, messages arereceived on the PDSCH of the first node.

The first device may be instructed by the node to switch back fromreading the PUSCH of the second device to reading the PDSCH of the firstnode (e.g., from the d2d mode to the normal mode of communication).

FIG. 7 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system 700 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. The computer system 700may be in the form of a computer system within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine may be connected (e.g., networked) to othermachines in a LAN, an intranet, an extranet or the Internet. The machinemay operate in the capacity of a server machine in client-server networkenvironment. The machine may be a personal computer (PC), a set-top box(STB), a server, a network router, switch or bridge or any machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine. Further, while only asingle machine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein. In one embodiment, the computersystem 700 may represent the first eNodeB 110, second eNodeB 210, firstuser equipment 120, second user equipment 220, or any of the corenetwork components 301-303 of FIG. 1.

The computer system 700 includes a processing device (processor) 702, amain memory 704 (e.g., read-only memory (ROM), flash memory, dynamicrandom access memory (DRAM) such as synchronous DRAM (SDRAM)), a staticmemory 706 (e.g., flash memory, static random access memory (SRAM)) anda data storage device 718, which communicate with each other via a bus730.

The processing device 702 represents one or more general-purposeprocessing devices such as a microprocessor, central processing unit orthe like. More particularly, the processing device 702 may be a complexinstruction set computing (CISC) microprocessor, reduced instruction setcomputing (RISC) microprocessor, very long instruction word (VLIW)microprocessor or a processor implementing other instruction sets orprocessors implementing a combination of instruction sets. Theprocessing device 702 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor or the like. The processing device 702 is configuredto execute the processing logic 726 for performing the operations andsteps discussed herein.

The computer system 700 may further include a network interface device708. The computer system 700 also may include a video display unit 710(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), analphanumeric input device 712 (e.g., a keyboard), a cursor controldevice 714 (e.g., a mouse) and a signal generation device 716 (e.g., aspeaker).

The data storage device 718 may include a computer-readable medium 728on which is stored one or more sets of instructions 722 (e.g.,instructions to perform the method 500 of FIG. 5 or the method 600 ofFIG. 6) embodying any one or more of the methodologies or functionsdescribed herein. The instructions 722 may also reside, completely or atleast partially, within the main memory 704 and/or within processinglogic 726 of the processing device 702 during execution thereof by thecomputer system 700, the main memory 704 and the processing device 702also constituting computer-readable media. The instructions 722 mayfurther be transmitted or received over a network 720 via the networkinterface device 708.

While the computer-readable storage medium 728 is shown in an exemplaryembodiment to be a single medium, the term “computer-readable storagemedium” or “computer-readable medium” should be taken to include asingle medium or multiple media (e.g., a centralized or distributeddatabase and/or associated caches and servers) that store the one ormore sets of instructions. The term “computer-readable storage medium”shall also be taken to include any medium that is capable of storing,encoding or carrying a set of instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present invention. The term “computer-readablestorage medium” shall accordingly be taken to include, but not belimited to, solid-state memories, optical media and magnetic media.

The preceding description sets forth numerous specific details such asexamples of specific systems, components, methods and so forth, in orderto provide a good understanding of several embodiments of the presentinvention. It will be apparent to one skilled in the art, however, thatat least some embodiments of the present invention may be practicedwithout these specific details. In other instances, well-knowncomponents or methods are not described in detail or are presented insimple block diagram format in order to avoid unnecessarily obscuringthe present invention. Thus, the specific details set forth are merelyexemplary. Particular implementations may vary from these exemplarydetails and still be contemplated to be within the scope of the presentinvention.

In the above description, numerous details are set forth. It will beapparent, however, to one of ordinary skill in the art having thebenefit of this disclosure, that embodiments of the invention may bepracticed without these specific details. In some instances, well-knownstructures and devices are shown in block diagram form, rather than indetail, in order to avoid obscuring the description.

Some portions of the detailed description are presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared and otherwise manipulated. It has provenconvenient at times, principally for reasons of common usage, to referto these signals as bits, values, elements, symbols, characters, terms,numbers or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the above discussion, itis appreciated that throughout the description, discussions utilizingterms such as “determining”, “generating” or the like, refer to theactions and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (e.g., electronic) quantities within the computer system'sregisters and memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

Embodiments of the invention also relate to an apparatus for performingthe operations herein. This apparatus may be specially constructed forthe required purposes or it may comprise a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a computerreadable storage medium, such as, but not limited to, any type of diskincluding floppy disks, optical disks, CD-ROMs and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards or any type of media suitable forstoring electronic instructions.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein or it may prove convenient to construct a more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear from the description below.In addition, the present invention is not described with reference toany particular programming language. It will be appreciated that avariety of programming languages may be used to implement the teachingsof the invention as described herein.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other embodiments will beapparent to those of skill in the art upon reading and understanding theabove description. The scope of the invention should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

What is claimed is:
 1. A method comprising: determining, by a first basestation, that a first user equipment in wireless data communication withthe first base station is to be configured to receive message datadirectly from a second user equipment in wireless data communicationwith a second base station without the message data traversing a corenetwork based on a determination by the first base station that thefirst user equipment is in proximity to the second user equipment;receiving, by the first base station from the second base station viathe core network, downlink control channel data comprising (a) systeminformation of the second base station, (b) an indication of acommunication channel to be used by the first user equipment forreceiving message data directly from the second user equipment, whereinthe indication of a communication channel comprises at least one of atime and frequency, and (c) an identity of the second user equipment;transmitting, by the first base station to the first user equipment, thedownlink control channel data; and transmitting, by the first basestation to the first user equipment, instructions to configure the firstuser equipment to determine, using the downlink control channel data,the message data transmitted by the second user equipment on an uplinkdata channel of the second user equipment.
 2. The method of claim 1,wherein determining that the first user equipment is to be configured tocommunicate directly with the second user equipment comprisesdetermining that the first user equipment and second user equipment arepart of a single-party sub-network.
 3. The method of claim 2, whereinthe sub-network is at least one of an intelligent home network or anenterprise private network.
 4. The method of claim 1, wherein theidentity of the second user device comprises a Cell Radio NetworkTemporary Identifier (CRNTI) of the second user equipment.
 5. A methodcomprising: determining that a first device associated with a first nodeof a wireless communication network is to communicate one or moremessages directly with a second device associated with a second node ofthe wireless communication network without the one or more messagestraversing a core network of the wireless communication network based ona determination by the first node that the first device is in proximityto the second device; receiving, from the second node, control datacomprising system information of the second node, an identity of thesecond device, and an indication of channel resources to be used forcommunicating the one or more messages, wherein the indication of thechannel resources comprises at least one of a time period and afrequency band; transmitting, to the first device, the control data;transmitting, to the first device, instructions to configure the firstdevice to: receive one or more transmissions from the second device; anddetermine, using the control data, message data corresponding to atleast one of the one or more messages based on the one or moretransmissions.
 6. The method of claim 5, wherein the channel resourcescomprise at least one of a spreading code, a frequency hop pattern or anelectromagnetic (EM) polarity.
 7. The method of claim 5, wherein theidentity of the second device comprises a Cell Radio Network TemporaryIdentifier (CRNTI) of the second user device.
 8. The method of claim 5,wherein the instructions to configure the first device compriseinstructions to configure the first device to: receive a firsttransmission from the second device; determine, using the control data,acknowledgment data based on the first transmission; receive a secondtransmission from the second device; and determine, using the controldata, the message data based on the second transmission.
 9. The methodof claim 8, wherein the acknowledgement data is used by the first deviceto schedule retransmission of at least one of the one or more messagesto the second device.
 10. The method of claim 8, wherein the controldata comprises data from a physical downlink control channel (PDCCH) ofthe second node, wherein the first transmission is a transmission on aphysical uplink control channel (PUCCH) of the second device, and thesecond transmission is a transmission on a physical uplink sharedchannel (PUSCH) of the second device.
 11. The method of claim 5, whereinthe determination that the first device and second device are inproximity to each other is based on a comparison by the first node of afirst access point name requested by the first device and a secondaccess point name requested by the second device.
 12. The method ofclaim 5, wherein determining that the first device is to be configuredto communicate one or more messages directly with the second devicecomprises determining that the first device and second device are partof a single-party sub-network.
 13. The method of claim 5, whereindetermining that the first device is to be configured to communicate oneor more messages directly with the second device comprises receiving acommand indicating that the first device is to be configured tocommunicate directly with the second device.
 14. A method comprising:receiving, by a first device associated with a first node of a wirelesscommunication network, instructions to receive one or more messagesdirectly from a second device associated with a second node of thewireless communication network without the one or more messagestraversing a core network of the wireless communication network, whereinthe instructions are based on a determination by the first node that thefirst device is in proximity to the second device; receiving, from thefirst node, control data comprising system information of the secondnode, an identity of the second device, and an indication of a channelresource to be used by the first device for receiving message datadirectly from the device, wherein the indication of a channel resourcecomprises at least one of a time period and a frequency band; receiving,from the second device, the one or more messages; and determining, usingthe control data, message data corresponding to at least one of the oneor more messages.
 15. The method of claim 14, wherein receiving the oneor more messages comprises receiving the one or more messages using atleast a portion of the channel resource.
 16. The method of claim 15,wherein the channel resource comprises at least one of a spreading code,a frequency hop pattern or an electromagnetic (EM) polarity.
 17. Themethod of claim 15, wherein the identity of the second device comprisesa Cell Radio Network Temporary Identifier (CRNTI) of the second userdevice.
 18. The method of claim 15, further comprising: receiving, fromthe second device, one or more acknowledgements of transmissions by thefirst device; and determining, using the control data, acknowledgementdata based on the one or more acknowledgements to be used forretransmission of at least one of the transmissions by the first device.19. The method of claim 18, wherein the control data comprises data froma physical downlink control channel (PDCCH) of the second node, whereinthe one or more messages are transmissions on a physical uplink controlchannel (PUCCH) of the second device, and the one or moreacknowledgements are transmissions on a physical uplink shared channel(PUSCH) of the second device.